Do not use ifeval macros for Client OS - #5087
Open
maximiliankolb wants to merge 1 commit into
Open
Conversation
It is easier to look at the macro than finding out what the value of "client-os" is for certain builds or assemblies.
|
The PR preview for 0ef2f33 is available at theforeman-foreman-documentation-preview-pr-5087.surge.sh The following output files are affected by this PR: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes are you introducing?
Reduce number of "ifeval" macros.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
It is easier to look at the macro than finding out what the value of "client-os" is for certain builds or assemblies.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Contributor checklists
Please cherry-pick my commits into: